Repository navigation
ci: refresh workflow pins and allow dependency ranges - #119
Merged
Merged
Conversation
Keep CI on supported action runtimes and the current Semgrep release.
Exact pins block patch and minor updates. The lockfile still selects the installed versions.
chaitanyapotti
changed the title
hieu-w
approved these changes
Nov 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
The workflows pin old GitHub Actions majors and Semgrep 1.136.0. Current releases are
actions/checkoutv7.0.1,actions/setup-nodev7.1.0,actions/setup-pythonv7.1.0, and Semgrep 1.183.0.The root manifest also pins every direct dependency to one version. Compatible updates should stay open. The lockfile still selects the installed versions.
Jira Link
N/A
Description
actions/checkoutto3d3c42e5aac5ba805825da76410c181273ba90b1(v7.0.1) in the validate, release, and security workflows.actions/setup-nodeto949feb2413d6458794dcd2491c4babbbce0c15c1(v7.1.0) in the validate and release workflows.actions/setup-pythonto6d4fd22b20465ccc0f7354476588e8df7c9ca0e0(v7.1.0) in the security workflow.setuptools<81install limit stays in place.changesets/actionatae32849d5ba541f9ae29e40e22a623bc13562f51(v2.1.2). That pin is already the latest release.@changesets/cli,@lavamoat/harden,@types/node,typescript, andvite-plus.actions/setup-nodev7 caches npm whenpackage.jsoncontains apackageManagerfield. This repository has that field, so the validate and release workflows will use the npm cache.How has this been tested?
npm test -- packages/torus-scripts/test/security-scanner-workflow.test.ts. The test passed.npm install --package-lock-only --ignore-scripts --dry-run. npm reported the tree up to date.Screenshots (if appropriate)
N/A
Types of changes
Checklist
Note
Low Risk
Changes are limited to CI action pins, a security scanner version bump, and looser devDependency ranges—no runtime product logic.
Overview
Updates CI to current pinned GitHub Actions releases and a newer Semgrep build across validate, release, and security workflows.
Workflow pins:
actions/checkout→ v7.0.1,actions/setup-node→ v7.1.0 (validate + release),actions/setup-python→ v7.1.0 (security), and Semgrep 1.136.0 → 1.183.0 (still withsetuptools<81).changesets/actionis unchanged.Dependency specs: Several root
devDependenciesmove from exact versions to caret ranges (@changesets/cli,@lavamoat/harden,@types/node,typescript,vite-plus), with matchingpackage-lock.jsonupdates.With
packageManageralready set inpackage.json, setup-node v7 should start using npm caching in validate and release jobs.Reviewed by Cursor Bugbot for commit 121f68f. Bugbot is set up for automated code reviews on this repo. Configure here.